Paper / Spigot
Velocity
ViaProxy
Standalone If your server is not running 26.3, you will need to install ViaVersion. For more information, see Supported versions.
Geyser-Spigot.jar.Geyser-Spigot.jar in the plugins folder.Now open the file /plugins/Geyser-Spigot/config.yml. Find the part that starts with bedrock:, and change the lines shown below.
NetherNet is supported fully by 26.50+. If you'd like to also have working MOTD and player count for older versions, you will need to set up both NetherNet and Raknet.
bedrock:
port: 19132
transport: nethernet
Also accepts RakNet, for additional compatibility: some Bedrock versions, such as 26.40, fetch the server's MOTD and player count over RakNet. This option needs a separate UDP port for NetherNet.
bedrock:
port: 19132
webrtc-port: UDP_PORT
transport: both
UDP_PORTport. Open it for UDP.Restart the server.
Since you are self-hosting, you can choose the port freely; the default is 19132. Geyser uses it over both TCP and UDP, so it cannot be the port of the Paper / Spigot server.
Important: No other program can use the Geyser port, over either protocol. This includes programs that use UDP, such as voice chat mods or Query, and programs that use TCP, such as another server, a web map, or a website.
Connecting from the same network
On the same device as the server, connect with localhost or 127.0.0.1 as the address. Other devices in the same local network can use your local IPv4 address, which starts with 10. or 192.168..
Connecting from a different network
To let players from outside your network join, you need to make the Geyser port reachable from the internet.
webrtc-port for UDP.You have two options:
Geyser's built-in signaling server uses plain HTTP by default, so Minecraft shows players a "Trust on First Use?" prompt the first time they join. To avoid this prompt, serve signaling over HTTPS, as explained in HTTPS for NetherNet. Some external signaling services, such as Warden, provide HTTPS as well.
Geyser-Fabric.jar.Geyser-Fabric.jar in the mods folder.Now open the file /config/Geyser-Fabric/config.yml. Find the part that starts with bedrock:, and change the lines shown below.
NetherNet is supported fully by 26.50+. If you'd like to also have working MOTD and player count for older versions, you will need to set up both NetherNet and Raknet.
bedrock:
port: 19132
transport: nethernet
Also accepts RakNet, for additional compatibility: some Bedrock versions, such as 26.40, fetch the server's MOTD and player count over RakNet. This option needs a separate UDP port for NetherNet.
bedrock:
port: 19132
webrtc-port: UDP_PORT
transport: both
UDP_PORTport. Open it for UDP.Restart the server.
Since you are self-hosting, you can choose the port freely; the default is 19132. Geyser uses it over both TCP and UDP, so it cannot be the port of the Fabric server.
Important: No other program can use the Geyser port, over either protocol. This includes programs that use UDP, such as voice chat mods or Query, and programs that use TCP, such as another server, a web map, or a website.
Connecting from the same network
On the same device as the server, connect with localhost or 127.0.0.1 as the address. Other devices in the same local network can use your local IPv4 address, which starts with 10. or 192.168..
Connecting from a different network
To let players from outside your network join, you need to make the Geyser port reachable from the internet.
webrtc-port for UDP.You have two options:
Geyser's built-in signaling server uses plain HTTP by default, so Minecraft shows players a "Trust on First Use?" prompt the first time they join. To avoid this prompt, serve signaling over HTTPS, as explained in HTTPS for NetherNet. Some external signaling services, such as Warden, provide HTTPS as well.
Geyser-NeoForge.jar.Geyser-NeoForge.jar in the mods folder.Now open the file /config/Geyser-NeoForge/config.yml. Find the part that starts with bedrock:, and change the lines shown below.
NetherNet is supported fully by 26.50+. If you'd like to also have working MOTD and player count for older versions, you will need to set up both NetherNet and Raknet.
bedrock:
port: 19132
transport: nethernet
Also accepts RakNet, for additional compatibility: some Bedrock versions, such as 26.40, fetch the server's MOTD and player count over RakNet. This option needs a separate UDP port for NetherNet.
bedrock:
port: 19132
webrtc-port: UDP_PORT
transport: both
UDP_PORTport. Open it for UDP.Restart the server.
Since you are self-hosting, you can choose the port freely; the default is 19132. Geyser uses it over both TCP and UDP, so it cannot be the port of the NeoForge server.
Important: No other program can use the Geyser port, over either protocol. This includes programs that use UDP, such as voice chat mods or Query, and programs that use TCP, such as another server, a web map, or a website.
Connecting from the same network
On the same device as the server, connect with localhost or 127.0.0.1 as the address. Other devices in the same local network can use your local IPv4 address, which starts with 10. or 192.168..
Connecting from a different network
To let players from outside your network join, you need to make the Geyser port reachable from the internet.
webrtc-port for UDP.You have two options:
Geyser's built-in signaling server uses plain HTTP by default, so Minecraft shows players a "Trust on First Use?" prompt the first time they join. To avoid this prompt, serve signaling over HTTPS, as explained in HTTPS for NetherNet. Some external signaling services, such as Warden, provide HTTPS as well.
All servers on the network must accept 26.3 Java clients, as Geyser imitates one.
Geyser-Velocity.jar.Geyser-Velocity.jar in the plugins folder.Now open the file /plugins/Geyser-Velocity/config.yml. Find the part that starts with bedrock:, and change the lines shown below.
NetherNet is supported fully by 26.50+. If you'd like to also have working MOTD and player count for older versions, you will need to set up both NetherNet and Raknet.
bedrock:
port: 19132
transport: nethernet
Also accepts RakNet, for additional compatibility: some Bedrock versions, such as 26.40, fetch the server's MOTD and player count over RakNet. This option needs a separate UDP port for NetherNet.
bedrock:
port: 19132
webrtc-port: UDP_PORT
transport: both
UDP_PORTport. Open it for UDP.Restart the server.
Since you are self-hosting, you can choose the port freely; the default is 19132. Geyser uses it over both TCP and UDP, so it cannot be the port of the Velocity server.
Important: No other program can use the Geyser port, over either protocol. This includes programs that use UDP, such as voice chat mods or Query, and programs that use TCP, such as another server, a web map, or a website.
Connecting from the same network
On the same device as the server, connect with localhost or 127.0.0.1 as the address. Other devices in the same local network can use your local IPv4 address, which starts with 10. or 192.168..
Connecting from a different network
To let players from outside your network join, you need to make the Geyser port reachable from the internet.
webrtc-port for UDP.You have two options:
Geyser's built-in signaling server uses plain HTTP by default, so Minecraft shows players a "Trust on First Use?" prompt the first time they join. To avoid this prompt, serve signaling over HTTPS, as explained in HTTPS for NetherNet. Some external signaling services, such as Warden, provide HTTPS as well.
All servers on the network must accept 26.3 Java clients, as Geyser imitates one.
Geyser-BungeeCord.jar.Geyser-BungeeCord.jar in the plugins folder.Now open the file /plugins/Geyser-BungeeCord/config.yml. Find the part that starts with bedrock:, and change the lines shown below.
NetherNet is supported fully by 26.50+. If you'd like to also have working MOTD and player count for older versions, you will need to set up both NetherNet and Raknet.
bedrock:
port: 19132
transport: nethernet
Also accepts RakNet, for additional compatibility: some Bedrock versions, such as 26.40, fetch the server's MOTD and player count over RakNet. This option needs a separate UDP port for NetherNet.
bedrock:
port: 19132
webrtc-port: UDP_PORT
transport: both
UDP_PORTport. Open it for UDP.Restart the server.
Since you are self-hosting, you can choose the port freely; the default is 19132. Geyser uses it over both TCP and UDP, so it cannot be the port of the BungeeCord server.
Important: No other program can use the Geyser port, over either protocol. This includes programs that use UDP, such as voice chat mods or Query, and programs that use TCP, such as another server, a web map, or a website.
Connecting from the same network
On the same device as the server, connect with localhost or 127.0.0.1 as the address. Other devices in the same local network can use your local IPv4 address, which starts with 10. or 192.168..
Connecting from a different network
To let players from outside your network join, you need to make the Geyser port reachable from the internet.
webrtc-port for UDP.You have two options:
Geyser's built-in signaling server uses plain HTTP by default, so Minecraft shows players a "Trust on First Use?" prompt the first time they join. To avoid this prompt, serve signaling over HTTPS, as explained in HTTPS for NetherNet. Some external signaling services, such as Warden, provide HTTPS as well.
plugins or mods folder. To run Geyser as a plugin or mod on your server instead, pick your server software in the tabs above.Geyser-ViaProxy.jar.Geyser-ViaProxy.jar in the plugins folder.Now open the file /plugins/Geyser/config.yml. Find the part that starts with bedrock:, and change the lines shown below.
NetherNet is supported fully by 26.50+. If you'd like to also have working MOTD and player count for older versions, you will need to set up both NetherNet and Raknet.
bedrock:
port: 19132
transport: nethernet
Also accepts RakNet, for additional compatibility: some Bedrock versions, such as 26.40, fetch the server's MOTD and player count over RakNet. This option needs a separate UDP port for NetherNet.
bedrock:
port: 19132
webrtc-port: UDP_PORT
transport: both
UDP_PORTport. Open it for UDP.Restart the server.
Since you are self-hosting, you can choose the port freely; the default is 19132. Geyser uses it over both TCP and UDP, so it cannot be the port of the ViaProxy server.
Important: No other program can use the Geyser port, over either protocol. This includes programs that use UDP, such as voice chat mods or Query, and programs that use TCP, such as another server, a web map, or a website.
If you use the ViaProxy GUI, you can use its account management to join online mode servers with Bedrock Edition. If you use the ViaProxy CLI and want Bedrock players to join your online mode server, install and set up Floodgate.
ViaProxy manages the auth-type setting itself, so its value in the config is ignored.
Connecting from the same network
On the same device as the server, connect with localhost or 127.0.0.1 as the address. Other devices in the same local network can use your local IPv4 address, which starts with 10. or 192.168..
Connecting from a different network
To let players from outside your network join, you need to make the Geyser port reachable from the internet.
webrtc-port for UDP.You have two options:
Geyser's built-in signaling server uses plain HTTP by default, so Minecraft shows players a "Trust on First Use?" prompt the first time they join. To avoid this prompt, serve signaling over HTTPS, as explained in HTTPS for NetherNet. Some external signaling services, such as Warden, provide HTTPS as well.
Now open the file config.yml. Find the part that starts with bedrock:, and change the lines shown below.
NetherNet is supported fully by 26.50+. If you'd like to also have working MOTD and player count for older versions, you will need to set up both NetherNet and Raknet.
bedrock:
port: 19132
transport: nethernet
Also accepts RakNet, for additional compatibility: some Bedrock versions, such as 26.40, fetch the server's MOTD and player count over RakNet. This option needs a separate UDP port for NetherNet.
bedrock:
port: 19132
webrtc-port: UDP_PORT
transport: both
UDP_PORTport. Open it for UDP.Restart Geyser.
Since you are self-hosting, you can choose the port freely; the default is 19132. Geyser uses it over both TCP and UDP.
Important: No other program can use the Geyser port, over either protocol. This includes programs that use UDP, such as voice chat mods or Query, and programs that use TCP, such as another server, a web map, or a website.
To choose which Java Edition server Geyser Standalone sends players to, find the java section:
java:
# The IP address of the Java Edition server.
address: 127.0.0.1
# The port of the Java Edition server.
port: 25565
# What type of authentication Bedrock players will be checked against when logging into the Java server.
# Can be "floodgate" (see https://wiki.geysermc.org/floodgate/), "online", or "offline".
auth-type: online
Change address to the Java server's address, or leave it as it is if the server runs on the same machine as Geyser. Then change port to the Java server's port. Set auth-type to floodgate if you set up Floodgate on the Java server, otherwise to online for an online mode server or offline for an offline mode server. To use Floodgate with Geyser Standalone, see Floodgate Setup.
Connecting from the same network
On the same device as the server, connect with localhost or 127.0.0.1 as the address. Other devices in the same local network can use your local IPv4 address, which starts with 10. or 192.168.. Alternatively, open Minecraft: Bedrock Edition and join the LAN server in the Friends tab.
Connecting from a different network
To let players from outside your network join, you need to make the Geyser port reachable from the internet.
webrtc-port for UDP.You have two options:
Geyser's built-in signaling server uses plain HTTP by default, so Minecraft shows players a "Trust on First Use?" prompt the first time they join. To avoid this prompt, serve signaling over HTTPS, as explained in HTTPS for NetherNet. Some external signaling services, such as Warden, provide HTTPS as well.
pkg install openjdk-21.wget -O Geyser-Standalone.jar https://download.geysermc.org/v2/projects/geyser/versions/latest/builds/latest/downloads/standalone.java -jar Geyser-Standalone.jar.Alternatively, there is an automated setup script for clean Termux installs. It might not work for everyone, so try it if the steps above do not work:
curl https://gist.githubusercontent.com/rtm516/e3e07d6595ee41e05a38b03c0f4d7a80/raw/install.sh | bash